Skip to content

Add PC6001VX - #5759

Merged
probonopd merged 1 commit into
masterfrom
discover/PC6001VX
Nov 3, 2026
Merged

probonopd merged 1 commit into
masterfrom
discover/PC6001VX

Conversation

@probonopd

Copy link
Copy Markdown
Member

Repository: https://github.com/eighttails/PC6001VX

Cross platform version of NEC PC-6001 emulator based on PC6001V

  • Stars: 51
  • Latest release: v4.5.0 (2026-09-09T09:34:03Z)
  • AppImage asset: PC6001VX-4.5.0-x86_64.AppImage
  • License: LGPL-2.1

Found by .github/workflows/discover-apps.yml, which looks for GitHub
repositories that publish AppImages but are not in the catalog yet. This
entry was not tested by a human; please review it before merging.

Discovered on GitHub as publishing AppImages on its releases, by
discover-apps.yml. Needs a maintainer's review.
@github-actions github-actions Bot added error-app-exits Test failed: the application quit or crashed right after starting error-glibc-too-new Test failed: built on a too new system (needs a newer glibc) labels Sep 28, 2026
@github-actions

Copy link
Copy Markdown
Contributor

❌ Test failure

@eighttails: this pull request adds the AppImage from your GitHub repository to the AppImage catalog; the test reports the following. Could you have a look?

Compatibility: not self-contained: uses the C library of the system; references glibc 2.39

  • The AppImage was built on a system that is too new. Please build it on the oldest still-supported Ubuntu LTS release so that it runs on all supported systems.
  • The application quit or crashed right after starting. The error below usually shows why.

First error in the log:

/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /run/firejail/appimage/AppRun)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.15' not found (required by /run/firejail/appimage/AppRun)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/AppRun)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libSDL2-2.0.so.0)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libSDL2-2.0.so.0)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libQt6Quick.so.6)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libQt6Quick.so.6)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libQt6Qml.so.6)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /run/firejail/appimage/usr/bin/../lib/libQt6Qml.so.6)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libQt6Gui.so.6)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libQt6Gui.so.6)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libQt6Network.so.6)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.15' not found (required by /run/firejail/appimage/usr/bin/../lib/libQt6Core.so.6)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libXcursor.so.1)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libxkbcommon.so.0)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libdecor-0.so.0)

Commit 61249a5. Full log

@eighttails

Copy link
Copy Markdown

@probonopd
I fixed backward compatibility and have confirmed that the latest version of master on GitHub can be built on Ubuntu 22.04.
eighttails/PC6001VX@a736136

@probonopd

Copy link
Copy Markdown
Member Author

/retest

@probonopd probonopd closed this Oct 1, 2026
@probonopd probonopd reopened this Oct 1, 2026
@github-actions

github-actions Bot commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

🌏 An invitation / 邀请

你好!非常感谢你制作了这个 AppImage!👋

我们注意到这个应用的界面或说明文档主要是中文的。AppImage 目录面向全球用户,默认以英文显示界面的应用可以被收录,并有机会触达世界各地更多的用户。

想请教一下:这个应用是否也可能对国际用户有帮助?如果是的话,作者是否愿意考虑把英文设为默认语言呢(例如根据系统语言环境 LANG / LC_* 自动选择,在非中文环境下回退到英文)?这样它就能被收录到目录中,让更多国际用户发现并使用它。

当然,在中文环境下依然可以默认显示中文——我们只是希望在其他语言环境下能有英文界面。🙏


Hi there, and thank you for making this AppImage! 👋

We noticed that this application's interface or documentation appears to be predominantly in Chinese. The catalog serves a worldwide audience, and applications that show an English interface by default can be included and reach many more users internationally.

Might this application also be of interest to users outside China? If so, would you consider making English the default — for example by following the system locale (LANG / LC_*) and falling back to English outside a Chinese locale? That would let us include it in the catalog so that many more people around the world can discover and enjoy it.

Chinese can of course remain the default in a Chinese locale — we would simply love an English fallback elsewhere. Thank you so much, and we look forward to your thoughts! 🙏

Commit 61249a5. Full log

@eighttails

Copy link
Copy Markdown

/retest

@probonopd probonopd closed this Oct 2, 2026
@probonopd probonopd reopened this Oct 2, 2026
@github-actions github-actions Bot removed error-app-exits Test failed: the application quit or crashed right after starting error-glibc-too-new Test failed: built on a too new system (needs a newer glibc) labels Oct 2, 2026
@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

🌏 An invitation / 邀请

你好!非常感谢你制作了这个 AppImage!👋

我们注意到这个应用的界面或说明文档主要是中文的。AppImage 目录面向全球用户,默认以英文显示界面的应用可以被收录,并有机会触达世界各地更多的用户。

想请教一下:这个应用是否也可能对国际用户有帮助?如果是的话,作者是否愿意考虑把英文设为默认语言呢(例如根据系统语言环境 LANG / LC_* 自动选择,在非中文环境下回退到英文)?这样它就能被收录到目录中,让更多国际用户发现并使用它。

当然,在中文环境下依然可以默认显示中文——我们只是希望在其他语言环境下能有英文界面。🙏


Hi there, and thank you for making this AppImage! 👋

We noticed that this application's interface or documentation appears to be predominantly in Chinese. The catalog serves a worldwide audience, and applications that show an English interface by default can be included and reach many more users internationally.

Might this application also be of interest to users outside China? If so, would you consider making English the default — for example by following the system locale (LANG / LC_*) and falling back to English outside a Chinese locale? That would let us include it in the catalog so that many more people around the world can discover and enjoy it.

Chinese can of course remain the default in a Chinese locale — we would simply love an English fallback elsewhere. Thank you so much, and we look forward to your thoughts! 🙏

PC6001VX

PC6001VX

Commit 61249a5. Full log

@eighttails

Copy link
Copy Markdown

@probonopd
There was an issue where multilingualization wasn't working, so I fixed it, and the screen in the test seems to be displayed in English, but I don't know why it's still being rejected because it's considered Chinese.

@eighttails

Copy link
Copy Markdown

/retest

@probonopd probonopd closed this Nov 2, 2026
@probonopd probonopd reopened this Nov 2, 2026
@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

✅ Test passed

Please check that the screenshot shows the application's main window.

PC6001VX

PC6001VX

Tested:

Compatibility: not self-contained: uses the C library of the system; references glibc 2.35

Names:

WARNING: The names of the repository, the AppImage and the README differ: repository 'PC6001VX', AppImage 'PC6001VX', README 'WARNING'

Warnings:

  • The repository, the AppImage and the README (whichever exist) call the application by different names (see the remarks below). Please check that they all belong to the same application, and that the name of the file in data/ is the right one.
  • The screenshot may show an error message; please check it.
  • The AppImage contains no update information, so users cannot update it with AppImageUpdate or similar tools. Please consider embedding it when building the AppImage (e.g., appimagetool -u) and publishing the .zsync file next to the AppImage; see https://docs.appimage.org/packaging-guide/optional/updates.html

Commit 61249a5. Full log

@eighttails

Copy link
Copy Markdown

The screenshot may show an error message; please check it.

This screenshot shows the program operating correctly.
Upon the initial launch, it asks for the location of the necessary files.
If you select "No," it will launch using the built-in compatible ROM files.

@probonopd
probonopd merged commit a3f2db5 into master Nov 3, 2026
10 of 12 checks passed
@probonopd
probonopd deleted the discover/PC6001VX branch November 3, 2026 19:45
@probonopd

Copy link
Copy Markdown
Member Author

/appstream

@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

How to add AppStream metadata (and your own screenshots)

The catalog page of an application can show a description, a summary, links and, above all, screenshots of your choice. They come from an AppStream metainfo file inside the AppImage.

1. Write the file. Save it as usr/share/metainfo/<id>.metainfo.xml inside the AppDir (the directory the AppImage is made from), where <id> is the <id> of the file, e.g. io.github.yourname.YourApp:

<?xml version="1.0" encoding="UTF-8"?>
<component type="desktop-application">
  <id>io.github.yourname.YourApp</id>
  <name>YourApp</name>
  <summary>One line saying what it does</summary>
  <metadata_license>CC0-1.0</metadata_license>
  <project_license>MIT</project_license>
  <description>
    <p>A few sentences about the application.</p>
  </description>
  <launchable type="desktop-id">yourapp.desktop</launchable>
  <url type="homepage">https://github.com/yourname/YourApp</url>
  <screenshots>
    <screenshot type="default">
      <caption>The main window</caption>
      <image>https://raw.githubusercontent.com/yourname/YourApp/main/screenshots/main.png</image>
    </screenshot>
  </screenshots>
  <releases>
    <release version="1.0.0" date="2024-01-31"/>
  </releases>
</component>
  • <launchable> names the .desktop file of the AppImage.
  • The screenshot is a web address (https://…) of a PNG image that stays there, e.g. a file in your repository. The file itself does not go into the AppImage.
  • <project_license> is the license of the application, as an SPDX identifier.

2. Check it: appstreamcli validate --no-net usr/share/metainfo/<id>.metainfo.xml (from the appstream package of your distribution).

3. Put it into the AppImage.

  • appimagetool, linuxdeploy, and other tools that build from an AppDir: copy the file to AppDir/usr/share/metainfo/ before building. appimagetool checks it while building.
  • electron-builder: add it to the AppImage with extraFiles, e.g. in package.json: "linux": { "extraFiles": [ { "from": "build/<id>.metainfo.xml", "to": "usr/share/metainfo/<id>.metainfo.xml" } ] }.
  • Other tools: see https://docs.appimage.org/packaging-guide/optional/appstream.html

4. Publish a new release with the new AppImage, then comment /retest on the pull request.

Note about screenshots: the automated test still runs the application and takes a screenshot of its own. The test needs it to check that the application starts and shows a window, so the test has to pass as before. But if the AppStream metadata names a screenshot, the catalog page shows that screenshot (the one marked type="default", else the first) instead of the automated one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants